Methods and apparatus for mounting a file system

ABSTRACT

One aspect involves mounting a file system stored on a CAS system. The file system has a directory structure that includes a plurality of directories arranged in a hierarchy and including a root directory at the top of the hierarchy. Each of the directories is represented by a content unit stored on the CAS system, the content unit having a content address that is computed based, at least in part, on at least a portion of the content of the content unit. The file system is mounted by specifying the content address of the content unit that represents the root directory and determining the file system to be mounted based on the content address of the content unit that represents the root directory.

FIELD OF THE INVENTION

The present invention relates to content addressable storage systems andfile systems.

DESCRIPTION OF THE RELATED ART

A file system is a logical construct that may be used to logicallystored data in an organized way. A typical file system is made up of aplurality of logical storage spaces referred to as directories orfolders. As used herein, the term “directory” and the term “folder” aresynonymous. The directories may be arranged in a hierarchical tree ormay be arranged in a flat structure. Data may be logically stored in alogical unit of storage referred to as a file and files may be logicallystored in the directories or folders of the file system.

The organization of files and directories in a file system may havelittle or nothing to do with the physical location at which the contentlogically stored in the files is stored on one or more physical storagedevice(s) underlying the file system. Thus, the file system softwaremaintains mapping information that maps the logical location of contentin the file system (i.e., a file) to the physical location of thatcontent on one or more underlying storage devices.

SUMMARY OF THE INVENTION

One embodiment is directed to a method of implementing a file system ina computer system comprising at least one content addressable storage(CAS) system that stores a plurality of content units each havingcontent, wherein each one of the content units has a content addressthat is computed based, at least in part, on at least a portion of thecontent of the one of the content units. The method comprises acts of:creating metadata that defines a directory structure of the file system,wherein the directory structure includes a plurality of directoryentries; and storing at least a portion of the metadata in at least oneof the plurality of content units on the at least one CAS system,wherein the at least one of the plurality of content units represents atleast one of the plurality of directories, and wherein the at least aportion of the metadata stored in the at least one content unit includesreferences to at least two of the plurality of content units that storecontent for two entries in the directory structure. Another embodimentis directed to at least one computer readable medium encoded with aplurality of instructions that, when executed, perform the method.

Another embodiment is directed to an apparatus to implement a filesystem in a computer system comprising at least one content addressablestorage (CAS) system that stores a plurality of content units eachhaving content, wherein each one of the content units has a contentaddress that is computed based, at least in part, on at least a portionof the content of the one of the content units. The apparatus comprisesat least one processor programmed to: create metadata that defines adirectory structure of the file system, wherein the directory structureincludes a plurality of directory entries; and store at least a portionof the metadata in at least one of the plurality of content units on theat least one CAS system, wherein the at least one of the plurality ofcontent units represents at least one of the plurality of directories,and wherein the at least a portion of the metadata stored in the atleast one content unit includes references to at least two of theplurality of content units that store content for two entries in thedirectory structure.

A further embodiment is directed to a method of creating a file systemto organize in a directory structure a plurality of content units storedon a content addressable storage system, wherein the plurality ofcontent units comprises at least a first content unit and a secondcontent unit, wherein the first content unit references the secondcontent unit. The method comprises acts of: creating a parent directorythat represents the first content unit; determining that the firstcontent unit references the second content unit; and based on thedetermination that the first content unit references the second contentunit, creating a file, logically stored in the parent directory, thatrepresents the second content unit. Another embodiment is directed to atleast one computer readable medium encoded with a plurality ofinstructions that, when executed, perform the method.

Another embodiment is directed to an apparatus to create a file systemto organize in a directory structure a plurality of content units storedon a content addressable storage (CAS) system, wherein the plurality ofcontent units comprises at least a first content unit and a secondcontent unit, wherein the first content unit references the secondcontent unit. The apparatus comprises at least one processor programmedto: create a parent directory that represents the first content unit;determine that the first content unit references the second contentunit; and based on a determination that the first content unitreferences the second content unit, create a file, logically stored inthe parent directory, that represents the second content unit.

A further embodiment is directed to a method of mounting a file systemstored on a content addressable storage system, the file system having adirectory structure that includes a plurality of directories arranged ina hierarchy wherein the plurality of directories includes a rootdirectory at the top of the hierarchy, wherein each of the plurality ofdirectories is represented by a content unit stored on the contentaddressable storage system, the content unit having a content addressthat is computed based, at least in part, on at least a portion of thecontent of the content unit. The method comprises: specifying thecontent address of the content unit that represents the root directory;and determining the file system to be mounted based on the contentaddress of the content unit that represents the root directory. Anotherembodiment is directed to at least one computer readable medium encodedwith a plurality of instructions that, when executed, perform themethod.

A further embodiment is directed to an apparatus to mount a file systemstored on a content addressable storage system, the file system having adirectory structure that includes a plurality of directories arranged ina hierarchy wherein the plurality of directories includes a rootdirectory at the top of the hierarchy, wherein each of the plurality ofdirectories is represented by a content unit stored on the contentaddressable storage system, the content unit having a content addressthat is computed based, at least in part, on at least a portion of thecontent of the content unit. The apparatus comprises at least oneprocessor programmed to: specify the content address of the content unitthat represents the root directory; and determine the file system to bemounted based on the content address of the content unit that representsthe root directory.

A further embodiment is directed to a method of allowing access to acontent unit stored on a content addressable storage system, the contentunit having a content address that is computed based, at least in part,on at least a portion of the content of the content unit. The methodcomprises acts of: providing a first interface to a file system in whichthe content unit is logically stored as a logical unit identified by alogical identifier, wherein the content unit is accessed in response toa request to the first interface to access the logical unit andidentifying the content unit via the logical identifier; and providing asecond interface through which the content unit can be accessed via thecontent address, wherein the content unit is accessed in response to arequest to the second interface to access the content unit andidentifying the content unit by the content address. Another embodimentis directed to at least one computer readable medium encoded with aplurality of instructions that, when executed, perform the method.

A further embodiment is directed to an apparatus to allow access to acontent unit stored on a content addressable storage system, the contentunit having a content address that is computed based, at least in part,on at least a portion of the content of the content unit. The apparatuscomprises at least one processor programmed to: provide a firstinterface to a file system in which the content unit is logically storedas a logical unit identified by a logical identifier, wherein thecontent unit is accessed in response to a request to the first interfaceto access the logical unit and identifying the content unit via thelogical identifier; and provide a second interface through which thecontent unit can be accessed via the content address, wherein thecontent unit is accessed in response to a request to the secondinterface to access the content unit and identifying the content unit bythe content address.

A further embodiment is directed to a method of implementing a filesystem in a computer system comprising at least one content addressablestorage (CAS) system that stores a plurality of content units eachhaving content, wherein each one of the content units has a contentaddress that is computed based, at least in part, on at least a portionof the content of the one of the content units. The method comprising anact of: in response to receiving a request to write a file in the filesystem from a source, storing the file in a content unit on the CASsystem before acknowledging to the source that file has been stored inthe file system. Another embodiment is directed to at least one computerreadable medium encoded with a plurality of instructions that, whenexecuted, perform the method.

A further embodiment is directed to an apparatus to implement a filesystem in a computer system comprising at least one content addressablestorage (CAS) system that stores a plurality of content units eachhaving content, wherein each one of the content units has a contentaddress that is computed based, at least in part, on at least a portionof the content of the one of the content units. The apparatus comprisesat least one processor programmed to, in response to receiving a requestto write a file in the file system from a source, store the file in acontent unit on the CAS system before acknowledging to the source thatfile has been stored in the file system.

A further embodiment is directed to a method for use in a computersystem comprising a content addressable storage system, a file systemhaving a directory structure comprising a plurality of directories, andmetadata describing the directory structure. The method comprises an actof: retrieving at least some of the metadata describing the directorystructure from the content addressable storage system, wherein the atleast some of the metadata describing the directory structure isretrieved from at least one content unit stored on the contentaddressable storage system, wherein the at least one content unit has acontent address that is computed based, at least in part, on at least aportion of the content of the at least one content unit. Anotherembodiment is directed to at least one computer readable medium encodedwith a plurality of instructions that, when executed, perform themethod.

A further embodiment is directed to an apparatus for use in a computersystem comprising a content addressable storage (CAS) system, a filesystem having a directory structure comprising a plurality ofdirectories, and metadata describing the directory structure. Theapparatus comprises at least one processor programmed to retrieve atleast some of the metadata describing the directory structure from thecontent addressable storage system, wherein the at least some of themetadata describing the directory structure is retrieved from at leastone content unit stored on the content addressable storage system,wherein the at least one content unit has a content address that iscomputed based, at least in part, on at least a portion of the contentof the at least one content unit.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a diagram of an example of a directory structure that may bedescribed by content units in a content addressable storage (CAS)system, in accordance with one embodiment of the invention;

FIG. 1B is a diagram of content units that describe the directorystructure of FIG. 1A, in accordance with one embodiment;

FIG. 2 is a diagram of a CAS system processing access requests forcontent units that describe a directory structure, in accordance withone embodiment;

FIG. 3 is a block diagram of a computer system in which a contentaddressable file system may be employed, in accordance with oneembodiment;

FIG. 4A is a graphical depiction of a file system directory structure;

FIG. 4B is an expanded view of the graphical depiction of the filesystem directory structure of FIG. 4A;

FIG. 5A is a diagram of a computer system in which a rendering managerthat renders a content addressable file system executes on a hostcomputer, in accordance with one embodiment.

FIG. 5B is a diagram of a computer system in which a rendering managerthat renders a content addressable file system executes on an appliance,in accordance with one embodiment.

FIG. 5C is a diagram of a computer system in which a rendering managerthat renders a content addressable file system executes on a CAS system,in accordance with one embodiment.

FIG. 6A is a diagram of a content unit that represents a file systemdirectory, in accordance with one embodiment;

FIG. 6B is a diagram of the content unit of FIG. 6A after an additionalfile is stored in the directory represented by the content unit, inaccordance with one embodiment;

FIG. 7 is a diagram of content units having mutable and non-mutableportions, in accordance with one embodiment;

FIG. 8 is a diagram of a chain of content units having mutable andnon-mutable portions, in accordance with one embodiment;

FIG. 9A is a diagram of content units stored on a CAS system;

FIG. 9B is a diagram of a directory structure created to represent therelationship between the content units of FIG. 9A, in accordance withone embodiment; and

FIG. 10 is a diagram showing two hosts having different platforms, tworendering managers and a CAS system in accordance with one embodiment.

DETAILED DESCRIPTION

Applicants have appreciated that conventional file systems havelimitations that may result in increased cost, longer access times,and/or wasted storage space. For example, because the content logicallystored in a typical file system is stored on relatively expensive media,such as a high-end or mid-range magnetic disk array, if the size of thedata stored in the file system outgrows the amount of storage spaceavailable, the purchase of additional expensive storage resources may berequired to provide additional storage space for the data of the filesystem. While some file systems have been stored on less expensivestorage media, such as tape or optical disc, the response time foraccess to the data is slower because the underlying storage device(e.g., the tape device or the optical disc device) is slower than themore expensive storage media devices.

Applicants have also appreciated that a large portion of the contentlogically stored in a file system may be fixed content. As used herein,fixed content refers to content that, once it is initially stored, isnever modified again. Fixed content may include, for example, financialreporting records, medical images (e.g., x-ray images and/or MRIimages), regulatory filings, such as SEC filings, and/or other suitablecontent.

It is common to create a back up copy of a file system, including thecontent of the file system, the structure of the file system, and theorganization of the content with the structure, at a regular interval,such as, for example, daily, weekly, and/or any other suitable interval.However, some conventional backup software programs do not distinguishbetween fixed content and mutable content (i.e., content that may bemodified after it is initially stored). Thus, the fixed content isbacked up each time a back up copy of the file system is created, eventhough the fixed content has not changed since the previous back up copyof the file system was created. While some backup software programs arecapable of performing incremental backups (i.e., backups that only backup the content that has changed), users typically perform an incrementalback up on a daily basis and a full backup weekly or monthly. Thisresults in wasted storage space on the backup storage media (i.e.,because multiple copies of the same content are stored on the backupstorage media). Further, the multiple copies of the same content maymake restore options take longer if it is ever needed to restore thefile system from a back up copy.

Software products exist that attempt to address some of theselimitations by reducing the amount of primary storage space needed tostore a file system. An example of such a software product is the LegatoDisk Extender™, which moves content stored in the file system to anarchive device and leaves a stub (that may be used to locate the contenton the archive device) in the file system where the content waspreviously stored. Thereafter, the software intercepts access requeststo the file system, determines if the content has been moved to thearchive storage device, and, if so, uses the stub to retrieve thecontent from the archive storage device, and places the content back inthe file system. Because some of the content may be stored on thearchive storage device (which may use less expensive storage media thanthe primary storage device underlying the file system), less storagespace on the more expensive primary storage media may be used. However,such software products may results in increased access times, becauserequested content may have to be retrieved from the archive storagedevice and moved to the primary storage device.

Conventional file systems often have object count limits that limit thenumber of files and/or other logical objects that may be stored therein.Thus, even though physical storage space is available to for storageadditional content, it may not be possible to storage additional contentin the file system because the limit on the number of logical objectspermitted in the file system has been reached.

The foregoing provide some examples of limitations that arise fromrendering a file system on a block I/O storage system. One embodiment ofthe invention is directed to a file system rendered on a CAS system.Various embodiments of the invention may address some or all of theabove-discussed limitations of file systems rendered on a block I/Ostorage system. However, some embodiments of the invention may addressonly some or not any of these limitations, and it should be appreciatedthat the invention is not limited to addressing or providing a solutionto any or all of these limitations of conventional file systems.

One embodiment is directed to a content addressable file system. Acontent addressable file system is a file system wherein the directorystructure of the file system is described by metadata stored in one ormore content addressable content units. A content addressable contentunit is a unit of content that is associated with a content address thatis computed, at least in part, from at least a portion of the content ofthe content unit. The content address of a content unit may then be usedto refer to and access the content unit. The directory structure may bedescribed by the content units in any suitable way, as this embodimentsis not limited in this respect.

In one embodiment, each directory in the directory structure and filestored in one of the directories in the directory structure can berepresented by a different content unit. A content unit that representsa directory may indicate, for example, in the content of the contentunit, any subdirectories and/or files of the directory it represents andthe content addresses of the content units that represent thosesubdirectories and/or files. An illustrative directory structure 100 isshown in FIG. 1A. Directory structure 100 includes a root directory 101,which has two subdirectories (i.e., accounting directory 103 andpersonal directory 109). Accounting directory 103 has subdirectoriesQ104 directory 105 and Q204 directory 107, and personal directory 109has subdirectories holiday pictures directory 111 and movies directory113. There are two files logically stored in holiday pictures directory111 (i.e., file A 115 and file B 117).

In accordance with one embodiment, the directory structure of FIG. 1Amay be described by content stored in content addressable content units.FIG. 1B shows one illustrative way of describing the directory structure100 of FIG. 1A by a plurality of content units. Content unit 119 has acontent address ‘XYZ’ and represents the root directory 101. The contentof content unit 119 indicates that there are two subdirectories of thedirectory represented by content unit 119. That is, content unit 119 hasa subdirectory named ‘accounting’ which is represented by a content unit121 having the content address ‘AAA’ and a subdirectory named ‘personal’which is represented by a content unit 127 having the content address‘BBB.’ Thus, content unit 121 represents the ‘accounting’ subdirectoryand has the content address ‘AAA’ and content unit 127 represents the‘personal’ subdirectory and has a content address ‘BBB.’ The content ofcontent unit 121 indicates that the accounting subdirectory has twosubdirectories (i.e., the Q104 directory represented by a content unit123 having the content address ‘CCC’ and the Q204 directory representedby a content unit 125 having the content address ‘DDD’). Thus, contentunit 123 represents the Q104 subdirectory and content unit 125represents the Q204 subdirectory.

Similarly, the content of content unit 127 indicates the personalsubdirectory also has two subdirectories (i.e., the holiday picturesdirectory represented by a content unit 129 having the content address‘EEE’ and the movies directory represented by a content unit 131 havingthe content address ‘FFF’). Content unit 129 (which represents theholiday pictures directory) indicates that there are two files stored inthe holiday pictures directory: file A which is represented by contentunit 133 having a content address ‘GGG’ and including the content offile A; and file B which is represented by content unit 135 having acontent address ‘HHH’ and including the content of file B. The contentunits that describe the directory structure may be stored in anysuitable physical location, as the invention is not limited in thisrespect.

In one embodiment, these content units may be stored on a contentaddressable storage (CAS) system. A CAS system is a storage system wherea content unit may be accessed by specifying the content address of thecontent unit (e.g., in an access request sent to the CAS system).

When the directories and files are stored as content units, anydirectory or file may be accessed based on knowledge of where it islocated in the file system and based on knowing the content address ofthe content unit representing the root directory. For example, if it isknown that file A is stored in the directory path root/personal/holidaypictures, the content of file A may be accessed as shown in FIG. 2. FIG.2 shows a CAS system 201 which stores the content units shown in FIG.1B. If it is known that the root directory of the directory structure isrepresented by the content unit having a content address ‘XYZ,’ arequest 203 may be sent to CAS system 201 to access the content unitcorresponding to the root directory and may identify the content unit byits content address (i.e., ‘XYZ’). In response, CAS system 201 mayreturn a response 205 that includes content unit 119, which representsthe root directory. Based on the content of this content unit, it may bedetermined that the content address of the content unit that representsthe ‘personal’ subdirectory is ‘BBB.’ Thus, a request 207 may be sent toCAS system 201 to access the content unit having the content address‘BBB’ and a response 209 may be returned by the CAS system that includescontent unit 127, which represents the ‘personal’ subdirectory. Based onthe content of content unit 127, it may be determined that the contentaddress of the content unit that represents the ‘holiday pictures’subdirectory is ‘EEE’ and a request 211 may be sent to CAS system 201for this content unit. In response, CAS system 201 may return a response213 that includes content unit 129, which corresponds to the ‘holidaypictures’ subdirectory. Based on the content of content unit 129, it maybe determined that File A, the desired file, has the content address‘GGG’ and a request 215 may be sent to CAS system 201 requesting thecontent unit having the content address ‘GGG.’ In response, CAS system201 may return a response 217 that includes content unit 133, whichstores the content of File A.

Applicants have appreciated that accessing a file by specifying a seriesof content addresses may be cumbersome to users, particularly those whoare accustomed to accessing files in a file system by inputting filesystem commands to a command line interface or by using a mouse tonavigate through a graphical representation of the file system. As usedherein, a user may be a human operator, an application program, acomputer, or any other suitable user.

In one embodiment, the file system may be accessed by a user in a mannersimilar to accessing conventional file systems. These user accesses maybe translated to content addressable requests to access a content unitor content unit related to the request and the appropriate informationmay be retrieved from the content unit and returned to the user. Thismay be done in any suitable way, as the invention is not limited in thisrespect.

An example is shown in FIG. 3, wherein a user access request to the filesystem (e.g., a command line command or a point and click on a graphicalrepresentation of the file system) may be received by rendering manager303. Rendering manager 303 may translate the access request into arequest, or set of requests, to a CAS system 301 on which the contentunits describing the file system are stored. Rendering manager 303 mayreceive the appropriate content unit or content units from CAS system301, extract the appropriate information from the content unit(s), andreturn the information to the user in any desired form (e.g., includingforms to which users are accustomed). In one embodiment, renderingmanager 303 utilizes a cache 305 to cache content units that form partof the directory structure received from CAS system 301. Thus, a requestto CAS system 301 need not be sent every time it is desired to access acontent unit stored thereon, as the content unit may already be storedin cache 305 and retrieved therefrom. However, the invention is notlimited to use of a cache, as in some embodiments, rendering manager 303may not cache content units received from the CAS system.

Rendering manager 303 may translate user accesses to content addressablerequests in any suitable way, as the invention is not limited in thisrespect. In one embodiment, command line interface file system commandsmay be received by rendering manager 303 and translated into contentaddressable access requests, which the rendering manager may then sendto CAS system 301. For example, as shown in Table 1 below, a user mayaccess the file system using Linux or UNIX file system commands. Theuser may input the command ‘cd root,’ which is a command to change thecurrent directory to the root directory. This command may be received byrendering manager 303 which, in response, may request the content unitcorresponding to the root directory from CAS system 301. If this contentunit is already stored in cache 305, rendering manager 303 need notrequest the content unit from CAS system 301, but may retrieve it fromcache 305. As can be seen in Table 1, the user need not specify thecontent address of the content unit corresponding to the root directoryin the ‘cd root’ command. Rather, rendering manger may determine thecontent address of the root directory without the content address beingspecified in the command. This may be done in any suitable way, as theinvention is not limited in this respect. Examples of techniques ofdetermining the content unit that represents the content address of theroot directory are discussed in greater detail below.

In response to the ‘cd root’ command received from the user, renderingmanager 303 may send a request to CAS system 301 to access thecorresponding content unit. As an example, the file system stored on CASsystem 301 may be the file system of the example of FIG. 1B, and therequest from rendering manager 303 to CAS system 301 may be a requestfor a content unit having the content address ‘XYZ.’ Thus, the CASsystem may, in response to the request, return content unit 119.

As shown in Table 1, the user next enters an ‘ls’ command. The ‘ls’command is a command to list the contents of the current directory(which is now the root directory). Rendering manager 103 may receive the‘ls’ command and, in response, may determine the content of the rootdirectory. This may be done in any suitable way as the invention is notlimited in this respect. For example, the contents of the root directorymay be determined by reading the content of content unit 119, whichrepresents the root directory. Content unit 119 indicates that there aretwo subdirectories of the root directory (i.e., the accountingsubdirectory and the personal subdirectory), thus in response to the iscommand, rendering manager 303 may cause the contents of the directoryto be displayed to the user, as shown in Table 1.

The user may subsequently input the command ‘cd personal’ which is acommand to change the current directory to the ‘personal’ subdirectoryof the root directory. In response, rendering manager 303 may determinethe content address of the content unit that represents the ‘personal’subdirectory and may send a request to CAS system 301 to access thecontent unit. As shown in Table 1, the user may then input another ‘ls’command to list the contents of the current directory (i.e., the‘personal’ directory) and rendering manager 303 may read the contents ofthe content unit (i.e., content unit 127) that represents the ‘personal’directory and cause them to be displayed to the user. Content unit 127indicates that the ‘personal’ directory has a ‘holiday pictures’subdirectory and a ‘movies’ subdirectory. Thus, this information may bedisplayed to the user, as shown in Table 1. The user may then input a‘cd holiday pictures’ command, which is a command to change the currentdirectory to the ‘holiday pictures’ directory. In response, renderingmanager 303 may request the content unit that represents this directoryfrom CAS system 301. As discussed above, if the user subsequently inputsan ‘ls’ command to list the contents of the current directory, renderingmanager 303 may read the contents of the content unit that representsthe ‘holiday pictures’ directory and cause this information to bedisplayed to the user.

TABLE 1 > cd root > ls accounting/ personal/ >cd personal >ls holidaypictures/ movies/ >cd holiday pictures >ls file A file B

Rendering manager 303 may also translate user accesses via a graphicaluser, interface (e.g., a graphical depiction of the directory structure)into content addressable access requests to the content units thatdescribe the file system. For example, as shown in FIG. 4, a graphicaldepiction of the file system includes an icon 401 for the rootdirectory. The user may input a command to see the contents of rootdirectory by selecting the ‘+’ symbol in box 403 associated with icon401 using an input device such as a mouse or a keyboard, by selectingthe folder icon itself, or in any other suitable way.

The users' actions on the graphical user interface may be translatedinto file system commands, such as those shown above in Table 1. Thismay be done in any suitable way and by any suitable software entity. Forexample, such translation may be performed by the operating system ofthe user's computer, by rendering manager 403, or by any other suitableentity. The selection of box 403 or the folder icon 401 may betranslated, for example, as an ‘ls’ command to see the contents of theroot directory. The translated command may be received be renderingmanager 303. In response, rendering manager 303 may access the contentsthe content unit corresponding to the root directory (i.e., content unit119), may read the information from this content unit, and may cause theinformation in content unit 119 indicating the contents of the rootdirectory to be displayed in graphical form to the user. For example, asshown in FIG. 4B, the accounting directory and the personal directory,respectively, are displayed as subdirectories of the root directory.

Rendering manager 303 may be implemented in any suitable way, as theinvention is not limited in this respect. In one embodiment, renderingmanager 303 may be implemented as a software program or a set ofsoftware routines. The rendering manager software may execute on anysuitable device or computer, as the invention is not limited in thisrespect. In one embodiment, rendering manager 303 may execute on a hostcomputer 501 through which a user accesses the file system, as shown inFIG. 5A. FIG. 5A shows the host computer 501, and a CAS system 509 onwhich the content units that describe the file system are stored. A usermay access the file system through a file system driver 515 of hostcomputer 501. Host computer 501 may provide (e.g., via the operatingsystem executing thereon) a file system interface 503, which may includea command line interface and/or a graphical user interface presented tothe user of host computer 501. File system interface 503 may interfacewith file system driver 515 to send user accesses to rendering manager505.

File system driver 515 may be configured to send user access requests torendering manager 505 in any suitable way. That is, the contentaddressable file system may be mounted on the host computer, forexample, by including the content address of the content unit thatrepresents the root directory of the content addressable file system ina mount command and specifying the rendering manager 505 as the sourcedevice. As a result, access requests to the content addressable filesystem may be forwarded to rendering manager 505 through file systemdriver 515, and rendering manager 505 may provide information, includingthe content of files and directory structure information, back to theuser through file system driver 515.

Rendering manager 505 may translate the user commands into contentaddressable access requests and may request any content units stored onCAS system 509 to retrieve information for responding to the accessrequests. Rendering manager 505 may then extract the information neededto respond to the request and may provide this information to filesystem driver 515 so that file system interface 503 may display theinformation to the user.

Write requests (i.e., requests to create content stored in a file in thefile system) originated by a source (e.g., a human user, an applicationprogram, or a host computer) may be received by rendering manger 505.Rendering manager may translate the write request into a contentaddressable access request to store the content in a content unit on CASsystem 509. After the CAS system 509 has stored the content in a contentunit, CAS system 509 may acknowledge to rendering manager 505 that thefile has been stored. Rendering manager 505 may forward thisacknowledgment to the source of the write request.

In one embodiment, the content address of the content unit thatrepresents the root directory may be provided to the rendering manager.This may be done in any suitable way, as the invention is not limited inthis respect. For example, the content address of the root directory maybe specified in the mount command to mount the content addressable filesystem.

In another embodiment one or more, profile content units may be used todetermine the content address of the content unit that represents theroot directory. A profile content unit is a content unit stored on thecontent addressable storage system that is associated with a particularuser (e.g., via a login name). The profile content unit for a user maybe created at any suitable time and may include any suitable informationrelating to the user.

For example, the profile content unit may be created when a user firstcreates a content addressable file system to be stored on the CAS systemand the profile content unit may include, for example, the contentaddress of the content unit that represents the root directory of thefile system that the user accesses. In some embodiments, the profilecontent unit may include multiple content addresses for multiple contentunits, wherein each of the content units represents the root directoryof a different file system. Thus, a user may have access to multipledifferent file systems that each is stored on the CAS system.

To determine the content address of the content unit that represents theroot directory, the rendering manager may send an access request to theCAS system for the profile content unit of the user (e.g., based on theidentity of the host computer or the identity of the user logged in tothe host computer) requesting to mount the file system. The renderingmanager may then retrieve the content address of the content unit thatrepresents the root directory from the profile content unit.

The network address of the CAS system (e.g., the IP address when used ina TCP/IP network) may be provided to the rendering manager so that itmay determine where (i.e., to what network address) to send the contentaddressable access requests. The network address may be provided in anysuitable way, as the invention is not limited in this respect. Forexample, in one embodiment, the network address of the CAS system may bespecified in the mount command to mount the content addressable filesystem and once it is specified, the rendering manager may store it forlater use. In another embodiment, the rendering manager may beconfigured by the user to use a particular network address, or theoperating system of the host computer may be configured to provide aparticular network address to the rendering manager.

In another embodiment, the rendering manager may be implemented on anappliance that is separate from the host computer and the CAS system,rather than on the host computer. For example, as shown in FIG. 5B, thehost computer executes file system interface 503, which may provide acommand line interface or graphical user interface to the user. Filesystem interface 503 interfaces with network file system client 511,which is capable of communicating (e.g., over a network or other medium)with a network file system server.

Appliance 517 implements a network file system server 513 and renderingmanager 505. Rendering manager 505 communicates (e.g., over a network orother medium) with CAS system 509. A user may access the contentaddressable file system through file system interface 503. Network filesystem client 511 may then send the access requests to network filesystem server 513, which forwards the access requests to renderingmanager 505. Rendering manager 505 may operate as discussed above toretrieve content units that include directory structure information andthe content of files from CAS system 509 and may provide thisinformation to the user via network file system server 513. As discussedabove, rendering manager 505 optionally may store information receivedfrom CAS system 509 in cache 507 so that if the information issubsequently accessed, it may not be necessary to retrieve theinformation again from CAS system 509.

Network file system client 511 and network file system server 513 mayimplement any type of network file system, as the invention is notlimited in this respect. For example, network file system client 511 andserver 513 may implement the network file system (NFS) or the commoninterne file system (CIFS).

In another embodiment, the rendering manager may be implemented on theCAS system. For example, as shown in FIG. 5C, host computer 501 executesfile system interface 503 and network file system client 511. CAS system509 executes network file system server 513 and rendering manager 505.Rather than forwarding access requests to an appliance, as in FIG. 5B,network file system client 511 forwards access requests to network filesystem server 509 executing on CAS system 509. Network file systemserver 509 may then forward these access requests for processing torendering manager 505, which is implemented on the CAS system.

In one embodiment, content units that describe the directory structuremay include content in addition to the information describing thedirectory structure. For example, a content unit corresponding to the‘holiday pictures’ directory (FIG. 1A) might, in addition to indicatingthat File A and File B are stored in that directory, provide metadataabout the content of File A and/or the content of File B. Such metadatamight indicate that File A is a picture having the caption “ChristmasDinner” and that File B is a picture having the caption “BeachVacation.”

The metadata in a content unit may be formatted in any suitable way, asthe invention is not limited in this respect. In one embodiment, themetadata is formatted according to the extensible markup language (XML).

Applicants have appreciated that users may desire to view the metadatathat is included in a content unit (including the directory structureinformation) and may also desire to know the content address of thecontent unit that represents a particular directory or file (even thoughit is not required to have the content address to access the contentunit). This may be done in any suitable way, as the invention is notlimited in this respect. In one embodiment, rendering manager 505 maypresent to the user (e.g., via the file system interface and/or otherintermediary software) one or more additional files as being logicallystored in each directory, even though there are no content units thatrepresent these files and no information stored in any of the contentunits that indicate the existence of such files. That is, for example,referring to FIG. 1B, content unit 119, which represents the rootdirectory, indicates that there are no files stored in the rootdirectory, but there are two subdirectories (i.e., accounting andpersonal). However, upon a request to view the contents of the rootdirectory, rendering manager 505 may, in addition to presenting theaccounting subdirectory and the personal subdirectory, present one ormore additional files. The one or more additional files, referred toherein as virtual files, are presented to allow a user to access themetadata and/or the content address of a content unit. A virtual filemay be thought of as being virtually stored in a directory of thedirectory structure.

In one embodiment, the rendering manager may present two virtual filesas being virtually stored in each directory or subdirectory. The firstvirtual file may be a CAS-ID file. When a user accesses the content of aCAS-ID file, rendering manager 505 may return the content address of thecontent unit that represents the directory in which the CAS-ID file isvirtually stored. For example, referring to FIG. 1B, if a user accessesthe CAS-ID file virtually stored in the root directory, renderingmanager 505 may return the content address ‘XYZ.’

The second virtual file presented by rendering layer 505 may be aCAS-meta file. When a user accesses the CAS-meta file, rendering manager505 may return the metadata stored in the content unit that representsthe directory in which the CAS-meta file is virtually stored. Thus, forexample, if a user accesses the CAS-meta file of the content unit thatrepresents the ‘holiday pictures’ directory, rendering manager 505 mayreturn the information indicating that there are two files logicallystored in the ‘holiday pictures’ directory (i.e., file A and file B) andmay also return the metadata described in the example above, indicatingthat file A is a picture and having the caption “Christmas Dinner” andthat file B is a picture having the caption “Beach Vacation.”

In the examples above, rendering manager 505 provides two virtual filesfor each directory, one associated with content address of a contentunit and another associated with the metadata of content unit. It shouldbe appreciated that the invention is not limited to providing both ofthese files, as in some embodiments only one of these files (either theCAS-ID file or the CAS-meta file) is provided. In another embodiment,only a single virtual file is provided, but the virtual file includesthe information of both the CAS-ID file and the CAS-meta file. Thus, forexample, when a user accesses such a virtual file, rendering manager 505may provide the content address of the content unit and the metadata ofthe content unit.

As discussed above, the content address for a content unit is computed,at least in part, from at least a portion of the content of the contentunit. This may be done in any suitable way, as the invention is notlimited in this respect. For example, the content of the content unit(or a portion thereof) may be input into a hash function which generatesa hash value using the input. This hash value may be used as the portionof the content address generated from the content of the content unit.Applicants have appreciated that while the content stored in a filesystem may be fixed content, it may be desirable to alter the directorystructure of the file system. Thus, for example, referring to FIG. 1B,while the content of content unit 133 may be fixed (i.e., because it isa photograph that it is not desirable to alter), it may be desirable tologically store another photograph in the directory represented bycontent unit 129 (i.e., the ‘holiday pictures’ directory) or to createanother directory that is a subdirectory of the ‘holiday pictures’directory (e.g., a ‘christmas pictures’ directory).

Applicants have appreciated that, if the content address is computedusing the entire content of the content unit, then changing the contentsof a directory may result in a change in the information stored in thecontent unit that represents the directory. For example, as shown inFIG. 6A, content unit 129 which represents the ‘holiday pictures’directory and includes an indication that file A and file B are storedtherein yields the content address ‘EEE.’ However, if a third file, fileC, is logically stored in the ‘holiday pictures’ directory, the contentof content unit 129 may be updated to reflect this addition, as shown inFIG. 6B. Because the content of content unit 129 has changed, thecontent unit may have a new content address, ‘RRR’. Thus, referring toFIG. 1B, the content of content unit 127, which represents the‘personal’ subdirectory, may be updated to indicate that the ‘holidaypictures’ subdirectory has a content address of ‘RRR,’ rather than‘EEE.’ Updating this information in content unit 127 may cause thecontent address of content unit 127 to change from ‘BBB’ to, forexample, ‘SSS.’Accordingly, the content of content unit 119, whichrepresents the root directory, may be updated to reflect the new contentaddress of the content unit that represents the ‘personal’ subdirectory.Of course, updating this information in content unit 119 may also causethe content address of content unit 119 to change. Thus, as can be seenfrom the example above, a change in the directory structure at aparticular level may cause a ripple effect which results in a change ofa content unit at every level in the directory structure that is higherthan the level at which the initial change occurred.

To address this, in one embodiment, the content of content units may bealtered without the alterations resulting in a change in the contentaddress of the content unit. This may be done in any suitable way, asthe invention is not limited in this respect.

For example, in one embodiment, the content address of a content unitmay be computed from a portion of the content unit that may neverchange. However, other portions of the content unit may be changed toreflect additions, modifications, or deletions to the directorystructure.

In an alternate embodiment, when the content of a directory changes, anew content unit may be created to reflect the change. For example, asshown in FIG. 7, content unit 129, which represents the ‘holidaypictures’ directory, indicates that file A and file B are storedtherein. If a third file, file C, is added to the ‘holiday pictures’directory, a new content unit 701 may be created reflecting this change.In addition, a pointer may be added into content unit 129 that points tothe new content unit (i.e., content unit 701). Content unit 701 may havea pointer that points back to the original content unit (i.e., contentunit 129). In addition, each content unit has two portions: a mutableportion and a non-mutable portion. For example, content unit 129 mayhave non-mutable portion 703 and mutable portion 705. Content unit 701has non-mutable portion 707 and mutable potion 709. The content addressof a content unit is computed using only the non-mutable portion of thecontent of the content unit. Thus, a change to the mutable portion ofthe content unit does not change the content address of the contentunit.

Thus, for example, if it is desired to access file C that is newly addedto the directory structure and is logically stored in the directory pathroot/personal/holiday pictures (FIG. 1B), the content of file C newlyadded to the directory structure shown in FIG. 1B, the rendering managermay send a request to the CAS system for the content unit thatrepresents the root directory by providing its content address (i.e.,‘XYZ’). In response, the CAS system may return content unit 119, whichrepresents the root directory. Based on the content of this contentunit, the rendering manager may determine that the content address ofthe content unit that represents the ‘personal’ subdirectory is ‘BBB’and may send a request to the CAS system for the content unit having thecontent address ‘BBB.’ In response, the CAS system may return contentunit 127, which represents the ‘personal’ subdirectory. Based on thecontent of content unit 127, it may be determined that the contentaddress of the content unit that represents the ‘holiday pictures’subdirectory is ‘EEE’ and rendering manager may send a request to theCAS system for this content unit. In response, the CAS system may returna content unit 129 which corresponds to the ‘holiday pictures’subdirectory. The rendering manager may recognized that content unit129, as shown in FIG. 7, includes a pointer to another content unithaving the content address ‘RRR’ that is an updated version of the‘holiday pictures’ subdirectory and may send a request to the CAS systemfor a content unit having the content address ‘RRR.’ In response, theCAS system may return content unit 701 and the rendering manager mayrequest the content unit that represents file C from the CAS systembased on the information therein.

Thus, as a result of the addition of file C into the ‘holiday pictures’directory, only the pointers in content unit 129 are changed and/oradded. It is not necessary to alter the content of any content unitsthat represent directories at higher levels in the directory structure,and therefore not necessary to alter the content addresses that are usedto link the content units together to form the directory structure.

If another file, file D, is subsequently stored in the ‘holidaypictures’ directory, as shown in FIG. 8, a new content unit 801 may becreated to reflect this addition. The pointers in the mutable portionsof content units 129 and 701 may be updated to indicate that contentunit 801 is the current content unit for the ‘holiday pictures’directory. Thus, when the rendering manager accesses content unit 129,it may recognize that the content unit includes a pointer to contentunit 801 and may use content 801 in place of content unit 129.

By maintaining the intermediate content units in a chain of contentunits (e.g., rather than deleting them), the directory structure may bereconstructed to reflect the structure of the file system at a specificpoint in time. For example, in FIG. 8, if after content unit 801 iscreated, it is desired to “roll back” the directory structure so that itis structured the way it was before File D was added to the ‘holidaypictures’ directory, then content unit 701 may become the “current”content unit and the pointers of content unit 129 may be updated toreflect this.

However, it should be appreciated that the invention is not limited tomaintaining intermediate content units in the chain. For example, insome embodiments, after content unit 801 is created, content unit 701may be deleted and the pointers of content unit 129 and content unit 801may be updated to reflect that these are the only two content units inthe chain.

The pointers in the mutable portion of a content unit may be implementedin any suitable way, as the invention is not limited in this respect. Inone embodiment, a pointer to another content unit may be an indicationof the content address of the content unit being referenced by thepointer. However, the invention is not limited in this respect, as thepointer may be implemented in any suitable way. For example, in FIG. 8,the pointer from content unit 129 to the current content unit (i.e.,content unit 801) may simply be the content address ‘ZZZ.’

Any suitable types of pointers may be maintained, as the invention isnot limited in this respect. For example, a chain of content units thatpreviously represented a particular directory along with the contentunit that currently represents the directory may be maintained. That is,each content unit in the chain may have a pointer to the previouscontent unit in the chain, a pointer to the first content unit in thechain, and a pointer to the next content unit in the chain. In addition,the first content unit in the chain may maintain a pointer to thecurrent content unit (i.e., the content unit that currently representsthe directory), which allows the rendering manager to locate the currentcontent unit upon retrieval of first content unit in the chain.

It should be appreciated that, in some embodiments, it is not necessaryto maintain all of these pointers. For example, in one embodiment, eachcontent unit may have a pointer only to the next content unit in thechain. The most recent content unit may be identified by following thechain of pointers to the end.

By maintaining a pointer or pointers in the mutable portion of a contentunit and not changing the metadata that describes the directorystructure in the non-mutable portion of the content unit, such metadatamay be verified to determine if it has been corrupted. Because thismetadata is not intentionally changed, and the content address computedusing the metadata (and any other data in the non-mutable portion of thecontent unit) is known, the content address may be recomputed using thenon-mutable portion of the content unit and it may be determined if therecomputed content address is the same as the originally computedcontent address. If the two content addresses are the same, it may beverified that the non-mutable content has not been altered or corrupted.If the two content addresses are different, then it may be recognizedthat the non-mutable content has been altered or corrupted and thenon-mutable content (or the entire content of the content unit) may berestored from a backup copy of the content unit.

In the examples described above, the rendering manager receives from theCAS system a content unit that includes a pointer to a more currentversion of the content unit, the rendering manager recognizes that amore current version of the content unit exists, and retrieves the morecurrent version from the CAS system. However, the invention is notlimited in this respect. For example, in an alternate embodiment thisrecognition may be performed by the CAS system instead of the renderingmanager. Referring to FIG. 8, when the rendering manager sends a requestto the CAS system for the content unit having the content address ‘EEE,’the CAS system may locate this content unit, recognize that the contentunit points to a more current version (i.e., content unit 801) and mayreturn content unit 801 in response to the request.

Changes to the directory structure may be performed either synchronouslyor asynchronously, as the invention is not limited in this respect. Whenperforming changes synchronously, a new content unit reflecting the newdirectory structure may be created and the pointers of previous versionsof the content unit may be updated immediately after a user alters thedirectory structure. When the changes to the directory structure areperformed asynchronously, a user may make a change to the directorystructure, but the new content unit is not created and the pointers ofprevious versions of the content unit are not updated until some timeafter the user makes these changes, for example, at a time when the CASsystem is not busy processing other requests or at a time when networktraffic is light. However, the updated directory information may bemaintained by the rendering manager in a scratch area so that if a userattempts to access a newly created or modified portion of the directorystructure that has not yet been created on the CAS system (i.e., due tothe asynchronous update), rendering manager may still provide currentinformation on the directory structure.

If a new file is stored in a directory and changes to the directorystructure are performed asynchronously, there may be a period of timeduring which no content address exists for the content unit thatrepresents the directory reflecting the addition of the new file,because the content unit has not yet been created on the CAS system.Thus, if a user attempts to access the CAS-ID file that is virtuallystored in the directory, rendering manager may not be able to respondwith the content address of the content unit that represents thedirectory (as it has not yet been created on the CAS system). In oneembodiment, when a user accesses the CAS-ID file virtually stored in adirectory for which a content unit has not yet been created, renderingmanager may send a request to the CAS system to create the new contentunit and update the pointers of the previous version or versions of thecontent unit so that a content address may be generated and returned tothe user in response to the user's access of the CAS-ID file. Thus, byaccessing the CAS-ID file virtually stored in a particular directory, auser may force the update of the content unit that represents thedirectory on the CAS system.

In the examples of above, new content units are created to reflectchanges to the directory structure caused by the addition of a file intoa directory. However, it should be appreciated that the techniquesdescribed above for handling modifications to the directory structuremay be employed for any modification to the directory structure and arenot limited to use with file additions. For example, such techniques maybe employed if a subdirectory is added to or deleted from the directorystructure, if a file is added to the directory structure, or any othermodification.

Further, in the examples above, a new content unit is created inresponse to a change to the directory structure of a file system so thatthe content of the original content unit may be updated with the contentof the new content unit. However, the invention is not limited toupdating the content of the original content unit to reflect the changeto a file system. Indeed, the content of content units stored on a CASsystem may be updated using the techniques described above for anysuitable reason. Further, these techniques may be employed on anycontent unit, and are not limited to use with content units thatrepresent directories in a directory structure. In some embodiments,such techniques for updating or modifying the content of content unitsmay be employed on CAS systems that are not used in the rendering of acontent addressable file system.

In one embodiment, a set of content units for a particular file systemmay be grouped into a virtual pool. Virtual pools are discussed indetail in application Ser. Nos. 10/910,985; 10/911,330; 10/911,248;10/911,247; and 10/911,360, listed in Table 2 below. A virtual pool is alogical grouping of content units. Content units may be logicallygrouped together in virtual pools for any suitable reason. For example,content units may be grouped together to control access to certaincontent units. That is, a first host computer may be permitted only toaccess content units in Virtual Pool A, while a second host computer maybe permitted only to access content units in Virtual Pool B.Additionally, different storage space quotas, retention periods, and/orreplication rules may be assigned to different virtual pools. Forexample, Virtual Pool A may include content units for a first filesystem, while Virtual Pool B may include content units for a second filesystem. A storage space quota of three gigabytes may be imposed onVirtual Pool A, such that once the content units in Virtual Pool A use 3gigabytes of storage space, no more content units may be added to thevirtual pool, while Virtual Pool B has a storage space quota of fivegigabytes. As another example, Virtual Pool A may have a retentionperiod of three years such that a content unit in Virtual Pool A may notbe deleted for a period of three years after its creation, while contentunits in Virtual Pool B have a retention period of two years. Moreover,virtual pools may different replication policies. For example, contentunits in Virtual Pool A may be replicated to a remote storage system,while content units in Virtual Pool B are not replicated.

In one embodiment, aspects of the present invention may be used with aCAS system that stores at least two different types of content units:blobs and CDFs as described in at least some of the Table 2applications. Data may be stored in logical objects referred to asblobs, while metadata (and optionally some data) is stored in logicalobjects referred to as content descriptor files (CDFs). CDFs mayreference blobs and other CDFs, while blobs do not reference othercontent units, and typically include data. Thus, CDFs may be used torepresent directories in the directory structure, while blobs may beused to represent files stored in the directory structure. That is, forexample, referring to FIG. 1B, content units 119, 121, 123, 125, 127,129, and 131 may be CDFs, while content units 133 and 135 may be blobs.Alternatively, content units 133 and 135 may be CDFs which eachreference another content unit which is the blob that stores the contentof the file. For example, content unit 133 may be a CDF that referencesanother blob (not shown) which stores the content of File A and contentunit 135 may be a CDF that references another which stores the contentof File B.

However, aspects of the invention are not limited to implementation on aCAS system that uses blobs and CDFs, as any suitable type(s) of contentunits may be used.

It may sometimes be desirable to share a content addressable file systemthat is stored on a CAS system with another user or mount the filesystem on another computer system. All that is needed to access a filesystem stored on a CAS system in accordance with the embodimentsdiscussed above, is the content address of the content unit thatrepresents the root directory of the file system. Thus, a first user mayshare access (e.g., via e-mail or otherwise) to a content addressablefile system with a second user by providing the second user with contentaddress of the root directory (which the first user may obtain, forexample, via the CAS-ID virtual file). The second user may then mountthe file system by providing the rendering manager with this contentaddress, as discussed above.

Applicants have appreciated that, in traditional file systems where thefile system mapping information and some or all of the data that islogically stored in the file system is locally stored on the user'ssystem, if the user's system crashes (e.g., due to hardware disk failureor another reason) the file system mapping information and data may haveto be restored from backup media (assuming that the file system waspreviously backed up). Restoring from backup may be a time consumingprocess, particularly where the file system is large. However, inembodiments that employ a content addressable file system as describedherein, if the user's system fails, the file system may be restored byspecifying the content address of the content unit that represents theroot directory to mount the file system. It is not necessary to copyfile system data from backup, because the content units that describethe directory structure and that store file data are stored on the CASsystem and were not lost or damaged, in the failure of the users'ssystem.

In one embodiment, the CAS system may mirror and/or replicates contentunits stored thereon. As used herein, mirroring a content unit refers tocreating a copy of the content unit on the CAS system and replicating acontent unit refers to creating a copy of the content unit on adifferent CAS system (e.g., a remote CAS system). Because the CAS systemautomatically performs mirroring and/or replication of content units, auser need not create a backup copy of the file system, as is often donewith traditional file systems.

In the examples above, content units were created to representdirectories and files as they were stored by a user. However, in oneembodiment, a directory structure may be created to organize contentunits previously stored on a CAS system (e.g., a CAS system that was notpreviously used to store file system metadata). This may be done in anysuitable way, as this aspect of the invention is not limited to anyparticular implementation technique. For example, as shown in FIG. 9A, aCAS system may have stored content units 901, 903, 905, 907, and 909.Content unit 901 may be a CDF which includes a reference to another CDF(i.e., content unit 903) and a blob (i.e., content unit 905). CDF 903may include references to two blobs (i.e., blob 907 and blob 909). Inone embodiment, these content units may be organized in a file system,for example, to provide a hierarchical sense of how the content islogically organized (or for any other suitable reason).

Thus, as shown in FIG. 9B, a CDF may be represented as a directory, witheach CDF that it references being represented as a subdirectory of thedirectory and each blob that it references being represented as a filestored in the directory. Thus, directory structure 911 includes adirectory ‘TTF’ which represents CDF 901. Directory ‘GHM’ is asubdirectory of directory ‘TTF’ and represents CDF 903. ‘CRC’ is a filestored in directory ‘TTF’ and represents blob 905 and files ‘ABC’ and‘DEF’ are files stored in directory ‘GHM’ and represent blobs 907 and909.

The directory structure created from existing content units may becreated in any suitable way, using any suitable process. As one example,a CAS system may be used in a company by three different departments,with the engineering department using the CAS system to store softwarebuilds, the marketing department using the CAS system to store marketingvideos, and the sales department using the CAS system to store salesagreements.

To create the directory structure, first the content addresses ofcontent units that are to form a part of the directory structure may beidentified. This may be done in any suitable way, as the invention isnot limited in this respect. In one embodiment, content units may beidentified by performing a time-based query on the CAS system. A timebased query is a request to identify all content units that were storedon the CAS system during a time range specified in the request. Thus,for example, in one embodiment where all content units stored on the CASsystem are to form a part of the directory structure, the time rangespecified in the request may be the range starting at the time when thefirst content unit was stored on the CAS system and ending at thecurrent time.

Next, for each content address identified, the content unit associatedwith the content unit may be accessed and information indicating whetherthe content unit was stored by the engineering department, the salesdepartment, or the marketing department may be retrieved from thecontent unit. Thus, it may be determined which content units are “sales”content units, which are “marketing” content units, and which are“engineering” content units.

Three new content units may then be created. The first of the newcontent units may be a content unit that represents a “sales” directoryand may include references to all of the “sales” content units, thesecond may be a content unit that represents a “marketing” directory andmay include references to all of the “marketing” content units, and thethird may be a content unit that represents an “engineering” directoryand may include references to all of the “engineering” content units.

In addition, a root content unit may be created that represents the rootdirectory of the file system. The root content unit may includereferences to the content unit that represents the “sales” directory,the content unit that represents the “marketing” directory, and thecontent unit that represents the “engineering” directory. The filesystem may then be mounted using the content address of the root contentunit.

In one embodiment in which the “sales” content units, “marketing”content units, and “engineering” content units were initially written ina hierarchical fashion, it may not be necessary to create a content unitthat represents the sales directory, a content unit that represents themarketing directory, and/or a content unit that represents theengineering directory.

In one embodiment of the invention, the storage space available for useby a particular content addressable file system is limited to the amountof free storage space on the CAS system. In another embodiment, thestorage space available for use by a content addressable file system maybe expanded beyond the amount of free storage space on the CAS system byproviding a second CAS system and creating a federation of CAS systemsthat includes both the first and second CAS systems. Federations of CASsystems are described in detail in application Ser. Nos. 10/787,337 and10/787,670 listed in Table 2 below. A federation is the grouping of twoor more CAS systems, wherein the group of CAS systems may be treated bya user as a single CAS system. Thus, the available storage capacity foruse in storing file system content may be expanded by adding additionalCAS systems into the federation.

The content addressable features of the file system provide the abilityto verify that the directory structure information and the contentstored in the file system have not been corrupted (e.g., when beingtransferred over a network or while stored on the CAS system) becausethis information is stored in content units. That is, in one embodiment,it may be determined if a content unit has been corrupted byre-computing the content address of the content unit. If the content ofthe content unit has been corrupted, the computation may yield adifferent content address than the original content address for thecontent unit and mirror copy or replicated copy of the content unit maybe used to replace the content unit. If the computation yields the samecontent address, it may be verified that the content of the content unithas not changed.

In the examples above, content units stored on a content addressablestorage system are accessed via file system commands generated by a useror another entity. In one embodiment, in addition to permitting accessto a content unit stored on the content addressable storage system via afile system, a user may access the content unit by sending a readrequest to the content addressable storage system that specifies thecontent address of the content unit. Thus, if the user knows the contentaddress of the content unit, the user may, instead of making a filesystem access that is translated into a content addressable accessrequest by the rendering manager, send an access request that specifiesthe content address of the content unit to the CAS system and mayreceive the content unit in response to this request. Such contentaddressable access requests are described in greater detail in theapplications listed below in Table 2.

In some embodiments, a content addressable file system that is stored ona CAS system may be portable. That is, the same content addressable filesystem may be mounted on both a first host computer that uses a firstplatform and a second host computer that uses a second platform. Thismay be done in any suitable way, as the invention is not limited in thisrespect.

For example, as shown in FIG. 10, host computer 1001 may use the Linuxplatform and host computer 1003 may use the Windows™ platform. A contentaddressable file system may be stored on CAS system 1009. Thus,rendering manager 1005 may be capable of converting file system callsfor a Linux platform to content addressable access requests to be sentto CAS system 1009 and rendering manager 1007 may be capable ofconverting file system calls for a Windows™ platform to contentaddressable access requests to be sent to CAS system 1009. However, bothrendering manager 1005 and 1007 may access the same set of content unitsthat make up a content addressable file system.

In one embodiment, rendering manager 1005 and rendering manager 1007 maystore file system metadata in content units using a common format sothat file system metadata stored in a content unit by rendering manager1005 may be read and understood by rendering manager 1007 and filesystem metadata stored in a content unit by rendering manager 1007 maybe read and understood by rendering manager 1005.

The file system may be mounted by both host computers at the same timeand used simultaneously, or may be used by one of the host computersonly when the file system is not in use (e.g., mounted) by the otherhost computer, as the invention is not limited in this respect. Further,in the embodiment shown in FIG. 10, two hosts having different platformsare capable of mounting the same content addressable file system.However, the embodiment of the invention is not limited to use with onlytwo different platforms or host computers, as the content addressablefile system may be used with any suitable number (e.g., one, three, ormore) of different platforms or host computers. In addition, theinvention is not limited to use with the two types of platforms given inthe example of FIG. 10 (i.e., Linux and Windows™), as any other platformfor which a rendering manager can translate file system calls intocontent addressable access requests may be used to mount a contentaddressable file system.

Additionally, in the examples above a separate rendering manager is usedby each host computer. However, the invention is not limited in thisrespect, as in some embodiments wherein the rendering manager isimplemented on an appliance or on the CAS system, multiple hostcomputers, regardless of the platform used, may use the same renderingmanager. In this respect, the rendering manger may be capable ofrecognizing file system calls of multiple different platforms andconverting those file system calls into content addressable accessrequests.

The above-described embodiments of the present invention can beimplemented on any suitable computer or system. Examples of suitablecomputers and/or systems are described in the patent applications listedbelow in Table 2 (collectively “the CAS applications”), each of which isincorporated herein by reference. It should be appreciated that thecomputers and systems described in these applications are only examplesof computers and systems on which the embodiments of the presentinvention may be implemented, as the invention is not limited toimplementation on any of these content addressable storage systems, orto content addressable storage systems at all.

TABLE 2 Title Ser. No. Filing Date Content Addressable 09/236,366 Jan.21, 1999 Information, Encapsulation, Representation, And Transfer AccessTo Content 09/235,146 Jan. 21, 1999 Addressable Data Over A NetworkSystem And Method For 09/391,360 Sep. 7, 1999 Secure Storage TransferAnd Retrieval Of Content Addressable Information Method And ApparatusFor 10/731,790 Dec. 9, 2003 Data Retention In A Storage System MethodsAnd Apparatus 10/731,613 Dec. 9, 2003 For Facilitating Access To ContentIn A Data Storage System Methods And Apparatus 10/731,796 Dec. 9, 2003For Caching A Location Index In A Data Storage System Methods AndApparatus 10/731,603 Dec. 9, 2003 For Parsing A Content Address ToFacilitate Selection Of A Physical Storage Location In A Data StorageSystem Methods And Apparatus 10/731,845 Dec. 9, 2003 For Generating AContent Address To Indicate Data Units Written To A Storage SystemProximate In Time Methods And Apparatus 10/762,044 Jan. 21, 2004 ForModifying A Retention Period For Data In A Storage System Methods AndApparatus 10/761,826 Jan. 21, 2004 For Extending A Retention Period ForData In A Storage System Methods And Apparatus 10/762,036 Jan. 21, 2004For Indirectly Identifying A Retention Period For Data In A StorageSystem Methods And Apparatus 10/762,043 Jan. 21, 2004 For IndirectlyIdentifying A Retention Period For Data In A Storage System Methods AndApparatus 10/787,337 Feb. 26, 2004 For Increasing Data Storage CapacityMethods And Apparatus 10/787,670 Feb. 26, 2004 For Storing Data In AStorage Environment Methods And Apparatus 10/910,985 Aug. 4, 2004 ForSegregating A Content Addressable Computer System Methods And Apparatus10/911,330 Aug. 4, 2004 For Accessing Content In A Virtual Pool On AContent Addressable Storage System Methods and Apparatus For 10/911,248Aug. 4, 2004 Including Storage System Capability Information In AnAccess Request To A Content Addressable Storage System Methods AndApparatus 10/911,247 Aug. 4, 2004 For Tracking Content Storage In AContent Addressable Storage System Methods and Apparatus For 10/911,360Aug. 4, 2004 Storing Information Identifying A Source Of A Content UnitStored On A Content Addressable System Software System For 11/021,892Dec. 23, 2004 Providing Storage System Functionality Software System For11/022,022 Dec. 23, 2004 Providing Content Addressable Storage SystemFunctionality Methods And Apparatus 11/022,077 Dec. 23, 2004 ForProviding Data Retention Capability Via A Network Attached StorageDevice Methods And Apparatus 11/021,756 Dec. 23, 2004 For ManagingStorage In A Computer System Methods And Apparatus 11/021,012 Dec. 23,2004 For Processing Access Requests In A Computer System Methods AndApparatus 11/021,378 Dec. 23, 2004 For Accessing Information In AHierarchical File System Methods And Apparatus 11/034,613 Jan. 12, 2005For Storing A Reflection On A Storage System Method And Apparatus For11/034,737 Jan. 12, 2005 Modifying A Retention Period Methods AndApparatus 11/034,732 Jan. 12, 2005 For Managing Deletion of Data MethodsAnd Apparatus 11/107,520 Apr. 15, 2005 For Managing The Storage OfContent Methods And Apparatus 11/107,063 Apr. 15, 2005 For Retrieval OfContent Units In A Time-Based Directory Structure Methods And Apparatus11/107,194 Apr. 15, 2005 For Managing The Replication Of Content MethodsAnd Apparatus 11/165,104 Jun. 23, 2005 For Managing the Storage OfContent In A File System Methods And Apparatus 11/165,103 Jun. 23, 2005For Accessing Content Stored In A File System Methods And Apparatus11/165,102 Jun. 23, 2005 For Storing Content In A File System

The above-described embodiments of the present invention can beimplemented in any of numerous ways. For example, the embodiments may beimplemented using hardware, software or a combination thereof. Whenimplemented in software, the software code can be executed on anysuitable processor or collection of processors, whether provided in asingle computer or distributed among multiple computers. It should beappreciated that any component or collection of components that performthe functions described above can be generically considered as one ormore controllers that control the above-discussed functions. The one ormore controllers can be implemented in numerous ways, such as withdedicated hardware, or with general purpose hardware (e.g., one or moreprocessors) that is programmed using microcode or software to performthe functions recited above.

In this respect, it should be appreciated that one implementation of theembodiments of the present invention comprises at least onecomputer-readable medium (e.g., a computer memory, a floppy disk, acompact disk, a tape, etc.) encoded with a computer program (i.e., aplurality of instructions), which, when executed on a processor,performs the above-discussed functions of the embodiments of the presentinvention.

The computer-readable medium can be transportable such that the programstored thereon can be loaded onto any computer environment resource toimplement the aspects of the present invention discussed herein. Inaddition, it should be appreciated that the reference to a computerprogram which, when executed, performs the above-discussed functions, isnot limited to an application program running on a host computer.Rather, the term computer program is used herein in a generic sense toreference any type of computer code (e.g., software or microcode) thatcan be employed to program a processor to implement the above-discussedaspects of the present invention.

It should be appreciated that in accordance with several embodiments ofthe present invention wherein processes are implemented in a computerreadable medium, the computer implemented processes may, during thecourse of their execution, receive input manually (e.g., from a user).

The phraseology and terminology used herein is for the purpose ofdescription and should not be regarded as limiting. The use of“including,” “comprising,” “having,” “containing”, “involving”, andvariations thereof, is meant to encompass the items listed thereafterand additional items.

Having described several embodiments of the invention in detail, variousmodifications and improvements will readily occur to those skilled inthe art. Such modifications and improvements are intended to be withinthe spirit and scope of the invention. Accordingly, the foregoingdescription is by way of example only, and is not intended as limiting.The invention is limited only as defined by the following claims and theequivalents thereto.

1. A method of mounting a file system stored on a content addressablestorage system, comprising: providing a root directory for a pluralityof directories for the file system, wherein the plurality of directoriesare provided in a hierarchical directory structure with the rootdirectory at the top of the hierarchy and wherein each of the pluralityof directories is represented by a content unit stored on the contentaddressable storage system and wherein the content addressable storagesystem includes at least one processor; determining a root contentaddress of a particular one of the content units that represents theroot directory by accessing a profile content unit stored on the contentaddressable storage system using a rendering manager that determines acontent address of the particular one of the content units and sends anaccess request to the content addressable storage system; anddetermining the file system to be mounted based on the root contentaddress.
 2. The method of claim 1, further comprising: presenting thefile system to a user.
 3. The method of claim 2, further comprising:receiving a request from the user to access a file, wherein the requestspecifies a file system location of the file in the file system; readingmetadata stored on the content addressable storage system; using themetadata to determine, based on the file system location provided in therequest, a content address for the content unit that stores content ofthe file; and using the content address to access the content unit. 4.The method of claim 2, wherein presenting the file system to a userincludes presenting a file as being stored in at least one of theplurality of directories, wherein the content of the file includesmetadata stored in one of the plurality of content units that representsthe at least one of the plurality of directories.
 5. The method of claim2, wherein presenting the file system to a user includes presenting afile as being stored in at least one of the plurality of directories,wherein the content of the file includes the content address stored ofone of the plurality of content units that represents the at least oneof the plurality of directories.
 6. The method of claim 1, wherein theprofile content unit is associated with a user and stores the contentaddress of the content unit that represents the root directory.
 7. Atleast one computer readable medium encoded with a plurality ofinstructions that, when executed, perform a method of mounting a filesystem stored on a content addressable storage system, the methodcomprising: providing a root directory for a plurality of directoriesfor the file system, wherein the plurality of directories are providedin a hierarchical directory structure with the root directory at the topof the hierarchy and wherein each of the plurality of directories isrepresented by a content unit stored on the content addressable storagesystem; determining a root content address of a particular one of thecontent units that represents the root directory by accessing a profilecontent unit stored on the content addressable storage system using arendering manager that determines a content address of the particularone of the content units and sends an access request to the contentaddressable storage system; and determining the file system to bemounted based on the root content address.
 8. The at least one computerreadable medium of claim 7, wherein the method further comprises:presenting the file system to a user.
 9. The at least one computerreadable medium of claim 8, wherein the method further comprises:receiving a request from the user to access the file, wherein therequest specifies a file system location of the file in the file system;reading metadata stored on the content addressable storage system; usingthe metadata to determine, based on the file system location provided inthe request, a content address for the content unit that stores thecontent of the file; and using the content address to access the contentunit.
 10. The at least one computer readable medium of claim 8, whereinpresenting the file system to a user includes presenting a file as beingstored in at least one of the plurality of directories, wherein thecontent of the file includes metadata stored in one of the plurality ofcontent units that represents the at least one of the plurality ofdirectories.
 11. The at least one computer readable medium of claim 8,wherein presenting the file system to a user includes presenting a fileas being stored in at least one of the plurality of directories, whereinthe content of the file includes the content address stored of one ofthe plurality of content units that represents the at least one of theplurality of directories.
 12. The at least one computer readable mediumof claim 7, wherein the profile content unit is associated with a userand stores the content address of the content unit that represents theroot directory.
 13. An apparatus to mount a file system stored on acontent addressable storage system, the apparatus comprising: at leastone processor programmed to: provide a root directory for a plurality ofdirectories for the file system, wherein the plurality of directoriesare provided in a hierarchical directory structure with the rootdirectory at the top of the hierarchy and wherein each of the pluralityof directories is represented by a content unit stored on the contentaddressable storage system; determine a root content address of aparticular one of the content units that represents the root directoryby accessing a profile content unit stored on the content addressablestorage system using a rendering manager that determines a contentaddress of the particular one of the content units and sends an accessrequest to the content addressable storage system; and determine thefile system to be mounted based on the root content address.
 14. Theapparatus of claim 13, wherein the at least one processor is furtherprogrammed to present the file system to a user.
 15. The apparatus ofclaim 14, wherein the at least one processor is further programmed to:receive a request from the user to access the file, wherein the requestspecifies a file system location of the file in the file system; readmetadata stored on the content addressable storage system; use themetadata to determine, based on the file system location provided in therequest, a content address for the content unit that stores the contentof the file; and use the content address to access the content unit. 16.The apparatus of claim 14, wherein the at least one processor isprogrammed to present a file as being stored in at least one of theplurality of directories, wherein the content of the file includesmetadata stored in one of the plurality of content units that representsthe at least one of the plurality of directories.
 17. The apparatus ofclaim 14, wherein the at least one processor is programmed to present afile as being stored in at least one of the plurality of directories,wherein the content of the file includes the content address stored ofone of the plurality of content units that represents the at least oneof the plurality of directories.
 18. The apparatus of claim 13, whereinthe at least one processor is disposed on the CAS system.
 19. Theapparatus of claim 13, wherein the CAS system is disposed in a computersystem comprising the CAS system and at least one host computer thataccesses at least some of the plurality of content units, and whereinthe at least one processor is disposed on the at least one hostcomputer.
 20. The apparatus of claim 13, wherein the CAS system isdisposed in a computer system comprising the CAS system, at least onehost computer that accesses at least some of the plurality of contentunits and at least one appliance that is separate from the at least onehost computer and the CAS system, and wherein the at least one processoris disposed on the at least one appliance.
 21. The apparatus of claim13, wherein the profile content unit is associated with a user andstores the content address of the content unit that represents the rootdirectory.